home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
BBS Toolkit
/
BBS Toolkit.iso
/
doors_1
/
lscan103.zip
/
LOGSCAN.DOC
next >
Wrap
Text File
|
1992-11-23
|
5KB
|
122 lines
Program Name: Logscanner 11-10-92
Disclaimer:
Use of this program is affirmation that you will not hold the Author
responsible in any way by the use of, or inability to use, this program.
Introduction:
This program came about by a friend asking if I could write a program
that would scan the BBS log looking for key words, and then write a
message in the BBS to the sysop or the user or both.
How it works:
Logscanner reads the config file specified in the command line and
then scans the BBS log looking for the matching string. Upon finding
a match it then enters a message in the BBS message area addressed to
the sysop, user, or one to both, according to the config file.
The program also make a log of all matches.
About Logscanner Config files:
You create the config files using the Logscanner editor. To invoke the
editor just type "logscan" without any additional command line parameters
You will then be on a menu asking if you want to edit a config file or
the test file for the messages. Choose "C" for config file. It will then
ask for the config file name, Enter the name with an extension of ".CFG".
If this file doesn't exsist in the current directory it will ask if you
want to create it or not. Enter "Y" to create it. You will then be put
into the config file editor.
The file created by the editor is in the following format.
1. drive:\path\name.log
2. drive:\path\
3. Y/N
4. !/@/%/&
5. Y/N
6. Y/N
7. "String"
1. This line is the drive, path and name of the BBS log file.
2. This line is the drive and path of the BBS config file (note,
must include trailing backslash).
3. This line tells the Logscanner whether or not to create a log file
for this config file.
4. This line indicates the mode for Logscanner to run in.
! - Indicates logfile only, no messages to enter.
@ - Indicates enter the message addressed to the sysop.
% - Indicates enter the message addressed to the user.
& - Indicates enter two messages, one to the sysop and one
to the user.
5. This line tells Logscanner to make the messages private or not.
6. This line tells Logscanner to use the sysop's and user's alias or
not in the To: and From: fields.
7. This is the "string" that Logscanner looks for in the BBS log file.
This string must match the one looked for exactly.
Logscanner .LGC text files:
You create the .LGC text files using the Logscanner editor. To invoke
the editor just type "logscan" without any additional parameters.
You will then be on a menu asking if you want to edit a config file
or the test file for the messages. Choose "T" for text file. It will
then ask for the text file name. Enter the name with an extension of
".LGC". If this file doesn't exist in the current directory it will ask
if you want to create it or not. Enter "Y" to create it. You will then
be put into the text file editor.
You have 11 lines available to write the message in. This is a very
simple, overwrite text editor. The arrow keys work as well as the HOME
and END keys. The BACKSPACE key functions as a left arrow key. The DELETE
key doesn't work. Also, CTRL-HOME goes to the start of the text page and
CTRL-END goes to the end of the text page. Once you have entered the
message as you want it, hit the ESC key and it will ask you if you are
finished editing the text file.
Running Logscanner:
To run the Logscanner in the scan mode type "logscan" with the
parameter of the config file without the .CFG extension (i.e.,
LOGSCAN CONFIG). (Note, there must be both a matching .CFG file
and .LGC text file.)
You need to delete or rename the log file after scaning it or you
will get repeats everytime you scan the log.
You need one config file and one text file for each string you
wish to scan for.
Registration:
This program is fully usable as is. The only sign that it is
unregistered is in each message it enters, there is a note at the
bottom stating that it is unregistered. You have as long as you like
to test this program.
Registration for this program is $5.00 (US).
Send letter with your Name as it appears in the Ezycom Config file,
and either a Fido, Adultlinks, ToadNet, PODSNet, or PIXNet address
or a mailing address, with a check or money order (DO NOT SEND
CASH) to the address below and I will send you a KEY file to you
that will put your name as who the program is registered to in the
messages posted.
To Robin K. Cook
PO Box 27034
San Antonio TX 78227
- or -
FidoNet # 1:387/635
(210) 674-4978 (14.4K V32b V42b)
enjoy